Looking good @Torakushi. I think it works well for the RN framework as its written currently.

There is a bigger rework that needs to be made for the React Native library to really take advantage of this, which is to make it multi-instance compatible. The typescript client and native code have to manage a Breez SDK instance over the RN bridge, which probably means communicating with an additional instance ID and emitting from the native code to a specific instance handler.

Right, I was thinking about tha, the multi instance PR will be quite more complex indeed (unless you meant that it has to be done right know?)

Anyway, here are some solutions to dig maybe to make the RN app multi-instances friendly:

• make "supportedEvent" dynamic, each time we call connect, we will add a new event in the supportedEvent. (But quite unsure that we can do that way? if we can, it will be easier!)

• If we can't make supportedEvent dynamic, we create a BreezSDKLogListenerDispatcher, that will listen to breezSdkNodeLog and then dispatch it to the right node_logger using an ID like you suggested for example.

Right, I was thinking about tha, the multi instance PR will be quite more complex indeed (unless you meant that it has to be done right know?)

@Torakushi these are good ideas that Ross and you are adding but certainly not part of this PR.

Happy to keep the scope for this PR minimal to accompany your other PR. I don't think there is a huge use-case for multi-instances in RN, so we can think about it more broadly in a follow-up PR.